Autogenerated HTML docs for v1.6.6.1-383-g5a9f 
diff --git a/git-config.txt b/git-config.txt index 2632928..543dd64 100644 --- a/git-config.txt +++ b/git-config.txt 
@@ -38,7 +38,7 @@  prepend a single exclamation mark in front (see also <<EXAMPLES>>).    The type specifier can be either '--int' or '--bool', to make -'git-config' ensure that the variable(s) are of the given type and +'git config' ensure that the variable(s) are of the given type and  convert the value to the canonical form (simple decimal number for int,  a "true" or "false" string for bool), or '--path', which does some  path expansion (see '--path' below). If no type specifier is passed, no @@ -125,16 +125,16 @@ 	List all variables set in config file.    --bool:: -	'git-config' will ensure that the output is "true" or "false" +	'git config' will ensure that the output is "true" or "false"    --int:: -	'git-config' will ensure that the output is a simple +	'git config' will ensure that the output is a simple 	decimal number. An optional value suffix of 'k', 'm', or 'g' 	in the config file will cause the value to be multiplied 	by 1024, 1048576, or 1073741824 prior to output.    --bool-or-int:: -	'git-config' will ensure that the output matches the format of +	'git config' will ensure that the output matches the format of 	either --bool or --int, as described above.    --path:: @@ -181,7 +181,7 @@  -----    If not set explicitly with '--file', there are three files where -'git-config' will search for configuration options: +'git config' will search for configuration options:    $GIT_DIR/config:: 	Repository specific configuration file. (The filename is @@ -198,12 +198,12 @@  If no further options are given, all reading options will read all of these  files that are available. If the global or the system-wide configuration  file are not available they will be ignored. If the repository configuration -file is not available or readable, 'git-config' will exit with a non-zero +file is not available or readable, 'git config' will exit with a non-zero  error code. However, in neither case will an error message be issued.    All writing options will per default write to the repository specific  configuration file. Note that this also affects options like '--replace-all' -and '--unset'. *'git-config' will only ever change one file at a time*. +and '--unset'. *'git config' will only ever change one file at a time*.    You can override these rules either by command line options or by environment  variables. The '--global' and the '--system' options will limit the file used